Method and system for dynamic binding in a storage area network

ABSTRACT

A system, method and computer program product for dynamically binding a server to a remote disk in a data center is provided. In a data center, servers and storage devices that manage multiple remote disks communicate over a switched fabric by using a standard protocol suite. The servers, storage devices and the switched fabric constitute a Storage Area Network (SAN). The devices present on the SAN are assigned a virtual identity, independent of their physical identity. The virtual identity of the servers facilitates the dynamic instantiation of the server images located on multiple remote disks on the servers.

BACKGROUND

The invention generally relates to remote booting in a Storage AreaNetwork (SAN). More specifically, the invention relates to a method andsystem for dynamically binding a server to a remote disk in a SAN.

A SAN is a network that interconnects servers and storage devices andenables high-speed transfer of data between them. Each storage deviceincludes multiple remote disks. Each remote disk stores several serverimages. A server image is a combination of an operating system, theoperating system configuration data, the application software, and theapplication configuration data, together with the SAN-relatedconfigurations. Further, each storage device includes a storagecontroller. The storage controller manages the multiple remote disks andprovides services such as RAID, read cache, write cache, Flash Copy,Peer-to-Peer Copy, and the like. The storage controller can enforce aone-to-one mapping between a server and a remote disk, which ensuresthat multiple servers do not access the remote disk concurrently. Thishelps to prevent data corruption. The SAN also includes a communicationinfrastructure that physically connects the servers to the storagedevices. The communication infrastructure manages the data transferbetween the servers and the storage devices by using a standardprotocol.

The Fibre Channel SAN (FC-SAN) with the Small Computer System Interface(SCSI) standard is one of the most common SAN technologies. There arethree major topologies for the FC-SAN, i.e., Point-to-Pont (FC-P2P),Arbitrated Loop (FC-AL) and Switched Fabric. The switched fabriccomprises a number of Fibre Channel switches (Director switches orFabric switches). These switches provide optimal interconnection betweenthe servers and the storage devices. The servers and storage devicesconnect to the switched fabric through a Fibre Channel Host Bus Adapter(HBA). Each HBA has a factory-installed World Wide Name (WWN), which isuniversally unique. The WWN facilitates communication between a serverand a storage device.

In SCSI terminology, communication occurs between an initiator and atarget. A server, acting as the initiator, sends a request to thestorage controller for a desired block or data segment stored on aremote disk that is referred to as the target.

Further, in FC-SW topology, the switched fabric is partitioned intosmaller groups to prevent interference, provide strict security, andease its overall management. This partitioning is known as zoning.Zoning controls access to the remote disks and manages visibility in theSAN, thereby avoiding unauthorized access to the remote disks.

The existing method for remote booting a server from a remote disk in aSAN includes recording a factory-assigned WWN of an HBA installed on theserver. Further, the remote disk, containing a desired server image, isidentified and the corresponding storage device is configured to provideaccess to the server. Subsequently, the firmware on the HBA of theserver is configured for remote booting from the remote disk assigned tothe server. Furthermore, the switched fabric is configured to authorizethe server to connect to the remote disk. These configuration settingsare persistent until explicitly modified by a data center administrator.

If an HBA that is installed on the server fails and a replacement HBA isinstalled, or server hardware failure occurs and the server is replacedwith a back-up server with a different HBA, booting the server is notpossible without appropriate configuration changes made by thedata-center administrator. However, these changes require manual,multi-step operator intervention and are error-prone. Moreover, it mayresult in data corruption and interruption in the data center service.

In present-day data centers, server repurposing is a common requirement.This involves a change in software, which includes an operating systemand a set of applications running on the server. Therefore, the serveris required to boot from a different remote disk. It is desirable tohave dynamic control over the number of servers deployed in thefunctional tiers of a business system, so that the capacity of thebusiness system can be dynamically adjusted to meet variable demands. Inthe state of the art, servers have a pre-determined function andconfiguration, as well as provision for anticipated maximal utilization.This results in inefficient utilization of network resources and anincrease in overall maintenance and operational costs.

There exist methods in the prior art that facilitate the process ofchanging the persistent binding between the servers and the remotedisks. One such technique, known as WWN spoofing or aliasing, enables anHBA of the server to assume a WWN other than the one installed on thehardware of the server. In the event of server hardware failure and areplacement server being brought in, the data center administratorassigns the WWN of the old HBA to the HBA of the replacement server.However, this method does not allow the same server to boot from oraccess-different remote disks at different times without operatorintervention before each such change.

Another technique, known as N_Port ID Virtualization (NPIV), allows aserver's HBA to assume multiple, non-persistent WWNs and access multipleremote disks by using different WWNs. NPIV enables an HBA port to serveas multiple logical ports, each with its own unique identity. A portlogin process involves the HBA port making a request for multiple IDsfrom attached SAN communication devices. Thereby, multiple logical portswith a unique World Wide Port and Node Names are created. The bindingbetween the logical ports and the remote disks is preserved, even aftera server function is moved to a new machine. However, the initializationof the HBA with additional WWNs can occur only after the server has aloaded operating system and an HBA driver is operational. Thus, thistechnique cannot be used for dynamic binding between a server and theremote disk, which contains a desired server image for booting.

In light of the above, there is a need for a method and system thatfacilitates dynamic non-persistent binding between a server and a remotedisk. Moreover, there is a need for a method and system that enablesnon-persistent binding without necessitating any permanent configurationchanges on the server, the storage devices, and the communicationdevices present on the SAN.

SUMMARY

An object of the invention is to dynamically bind a server to a remotedisk, for booting in a data center.

Another object of the invention is to facilitate a non-persistentbinding between the server and the remote disk, for booting in the datacenter.

Yet another object of the invention is to non-persistently instantiate avirtual World Wide Name (WWN) on a server, for booting from a remotedisk in the data center.

The invention provides a method, system and computer program product fordynamic, non-persistent binding of a server to a remote disk by using avirtual WWN.

The data center includes a plurality of servers and one or more storagedevices. Each storage device manages one or more remote disks. The datacenter also comprises a switched fabric to connect the plurality ofservers and the one or more storage devices. The servers, storagedevices and the switched fabric constitute a Storage Area Network (SAN).The data center also comprises a boot controller to manage the remotebooting of servers.

The boot controller dynamically selects a server image located on aremote disk, to boot on a server, based on the requirements of the datacenter. The boot controller assigns at least one virtual WWN to theremote disks. Further, the boot controller instantiates a virtual WWN onthe server. Subsequently, the server boots from the desired server imageby using the virtual WWN, which uniquely identifies the server,independent of the underlying hardware configuration. In anotherembodiment of the invention, a boot gateway, in conjunction with theboot controller, executes a staged booting of the server.

Therefore, the invention eliminates the use of persistent mappings andconfigurations to boot the server from the remote disk. The inventionsupports decoupling of the software environment and the configurationsfrom the hardware of the server. Further, the invention facilitates theimplementation of server repurposing in a data center.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention will hereinafter be described inconjunction with the appended drawings, provided to illustrate and notto limit the invention, wherein like designations denote like elements,and in which:

FIG. 1 is a block diagram illustrating a data center in which variousembodiments of the invention may be practiced;

FIG. 2 is a block diagram illustrating the data center, in accordancewith an embodiment of the invention;

FIG. 3 is a block diagram illustrating a boot configuration database, inaccordance with an embodiment of the invention,

FIG. 4 is a block diagram illustrating the data center, in accordancewith another embodiment of the invention;

FIG. 5 is a flowchart illustrating a method for dynamically binding aserver to a remote disk, in accordance with an embodiment of theinvention;

FIG. 6 is a flowchart illustrating a method for dynamically binding aserver to a remote disk, in accordance with another embodiment of theinvention;

FIG. 7 is a flowchart illustrating a method for dynamically binding aserver to a remote disk, in accordance with still another embodiment ofthe invention;

FIGS. 8A and 8B represent a flowchart illustrating a method fordynamically binding a server to a remote disk, in accordance with yetanother embodiment of the invention.

DETAILED DESCRIPTION OF EMBODIMENTS

Various embodiments of the invention provide a system and method fordynamically binding servers to remote disks in a data center. In a datacenter, a server is assigned a virtual identity, which is independent ofthe physical identity of the server. Further, a server image isdissociated from the server hardware and the network-related attributesof the server. The server image is instantiated dynamically on anysuitable server available in the data center by using the virtualidentity of the server.

FIG. 1 is a block diagram illustrating a data center 100 in whichvarious embodiments of the invention may be practiced. Data center 100includes at least one server. For example, data center 100 includes aserver 102 a, a server 102 b, and a server 102 c, hereinafter referredto as servers 102. Further, data center 100 includes one or more storagedevices, for example, a storage device 104 a, a storage device 104 b,and a storage device 104 c, hereinafter referred to as storage devices104. Each storage device 104 manages a plurality of remote disks. Forexample, storage device 104 a manages a remote disk 106 a and a remotedisk 106 b. Storage device 104 manages remote disk 106 throughspecialized equipment known as a storage controller (not shown in FIG.1).

Data center 100 includes a communication infrastructure 108. Servers102, storage devices 104 and communication infrastructure 108 constitutea SAN. Further, data center 100 includes a control network 110.

Each server 102 connects to communication infrastructure 108 through aHost Bus Adapter (HBA). For example, server 102 a connects tocommunication infrastructure 108 through HBA 112 a. Similarly, eachstorage device 104 connects to communication infrastructure 108 throughan HBA. For example, storage device 104 a connects to communicationinfrastructure 108 through HBA 114 a.

Servers 102 may be required to boot from a server image located on oneof remote disks 106, based on the functional requirements of data center100. Server 102 communicates with storage device 104 managing remotedisk 106, which contains the desired server image. Servers 102 andstorage devices 104 exchange data over the communication infrastructure108 by using pre-defined protocol suites. Control network 110 is aTCP/IP network with a pre-defined protocol suite. Servers 102 connect tocontrol network 110 through Ethernet Network Interface Cards (NICs) (notshown in FIG. 1). Storage devices 104 also connect to control network110. Further, each HBA 112 and HBA 114 is identified by a unique WorldWide Name (WWN) that is factory-installed. These WWNs facilitatecommunication between servers 102 and storage devices 104.

In various embodiments of the invention, servers 102 may be standaloneservers, virtual servers, web servers, virtual racks, chassis, and thelike. Further, communication infrastructure 108 may be a Fibre Channelwith Small Computer System Interface (SCSI) protocol suite, an Ethernet(TCP/IP) with an Internet Small Computer System Interface (iSCSI)protocol suite or Ethernet with Advanced Technology Attachment (ATA)protocol suite.

In various embodiments of the invention described henceforth,communication infrastructure 108 is a Fibre Channel Switched Fabric(FC-SW) with an SCSI protocol suite. Accordingly, communicationinfrastructure 108 will hereinafter be referred to as switched fabric108. It should be recognized by persons ordinarily skilled in the artthat various embodiments of the invention are equally applicable toother possible embodiments of communication infrastructure 108.

FIG. 2 is a block diagram illustrating a data center 200, in accordancewith an embodiment of the invention. Data center 200 includes servers102 (known as ‘initiators’ in SCSI parlance). Data center 200 alsoincludes one or more storage devices 104, which manage multiple remotedisks 106. Servers 102 access remote disks 106 (known as ‘targets’ inSCSI parlance) over switched fabric 108 through HBA 112. Servers 102,storage devices 104 and switched fabric 108 constitute a SAN. Further,data center 200 includes a boot controller 202 and a boot configurationdatabase 204.

Boot controller 202 is a specialized appliance or software operating onservers 102. Boot controller 202 and servers 102 communicate overcontrol network 110. Boot controller 202 facilitates dynamic,non-persistent binding between a server 102 and a remote disk 106 byusing a set of virtual WWNs. Dynamic assignment of virtual WWNs toremote disk generally means that the configuration settings related tothe assignment of virtual WWNs to remote disk 106 are doneinstantaneously by boot controller 202. Further, non-persistent bindingbetween server 102 and remote disk 106 generally means that theconfiguration settings related to the binding of server 102 and remotedisk-106 are temporary and are defined based on the functionalrequirements of data center 200. Virtual WWNs are universally uniquenames that identify the devices present on the SAN, independent ofphysical identity of the devices. The set of virtual WWNs and the set offactory-installed WWNs are mutually exclusive.

For example, boot controller 202 selects a first virtual WWN from theset of virtual WWNs and assigns it to storage device 104. Further, bootcontroller 202 selects one or more virtual WWNs from the set of virtualWWNs and assigns the one or more virtual WWNs to remote disk 106. In anembodiment of the invention, the assignment of virtual WWNs to remotedisk 106 is a static assignment, which is persistent in nature, untilexplicitly modified. Static assignment of virtual WWNs to remote disk106 generally means that the configuration settings related to theassignment of virtual WWNs to remote disk 106 are permanently orpersistent in nature. In an embodiment of the invention, the staticassignment may be performed by the data center administrator.

In another embodiment of the invention, the assignment of virtual WWNsto remote disk 106 is a dynamic assignment undertaken by boot controller202 by using standard management Application Programming Interfaces(APIs), for example, Simple Network Management Protocol (SNMP). Dynamicassignment of virtual WWNs to remote disk generally means that theconfiguration settings related to the assignment of virtual WWNs toremote disk 106 are done instantaneously by boot controller 202.Further, boot controller 202 communicates information related to theassignment of virtual WWNs to remote disk 106 to storage device 104 overcontrol network 110. In addition, virtual WWNs are also configured inswitched fabric 108.

Thereafter, based on the functional requirements of data center 200,boot controller 202 selects remote disk 106, which contains a desiredserver image. Subsequently, boot controller 202 dynamically maps one ofthe one or more virtual WWNs, assigned to remote disk 106, to server102.

Further, boot controller 202 manages boot configuration database 204.Boot configuration database 204 stores information related to thedynamic binding of server 102 with remote disk 106. The various modulesof boot configuration database 204 are explained in conjunction withFIG. 3.

In various embodiments of the invention, one or more HBAs 112 may bepresent in servers 102. Further, one or more boot controllers 202 may bepresent in data center 200. However, only one boot controller 202 isprovisioned to facilitate dynamic binding of server 102. Variousredundant devices constituting switched fabric 108 may also be presentin data center 200.

FIG. 3 is a block diagram illustrating a boot configuration database204, in accordance with an embodiment of the invention. Bootconfiguration database 204 includes a remote disk-to-virtual WWN mapping302, a server-to-remote disk mapping 304, a repository of virtual WWNs306, and a bootstrap program 308. Remote disk-to-virtual WWN mapping 302defines one or more virtual WWNs assigned to remote disk 106,authorizing only initiators with these virtual WWNs to access remotedisk 106. Remote disk-to-virtual WWN mapping 302 is updated by bootcontroller 202.

Further, server-to-remote disk mapping 304 defines server 102 asauthorized to access remote disk 106. This facilitates one-to-oneassociation between server 102 and remote disk 106. Server-to-remotedisk mapping 304 is dynamically updated by boot controller 202. In anembodiment of the invention, server-to-remote disk mapping 304 preventsthe concurrent access of servers 102 to remote disks 106.

Further, boot configuration database 204 includes repository 306 thatcontains a pool of virtual WWNs. Repository 306 contains virtual WWNsthat may be mapped uniquely to a device connected to switched fabric108. Boot configuration database 204 also contains bootstrap program 308that initiates the dynamic booting of servers 102 in data center 200.

FIG. 4 is a block diagram illustrating a data center 200, in accordancewith another embodiment of the invention. In addition to the elementsdescribed in conjunction with FIG. 3, data center 200 includes bootgateway 402. Boot gateway 402 is connected to remote disk 106 through aHost Bust Adapter (HBA-GW) 404 and is also connected to control network110.

Boot controller 202 assigns boot gateway 402 to facilitate booting of aset of servers 102. Further, boot controller 202 assigns a virtual WWNto remote disk 106, the virtual WWN uniquely identifying boot gateway402, independent of its physical identity. In an embodiment of theinvention, the assignment of the virtual WWN to remote disk 106 may beperformed statically by a data center administrator.

In another embodiment of the invention, the assignment of the virtualWWN to remote disk 106 may be performed dynamically by boot controller202. Subsequently, boot controller 202 communicates the mapping tostorage device 104 over control network 110. This authorizes bootgateway 402 to access remote disk 106.

The virtual WWN assigned to boot gateway 402 may either be performedstatically by the data center administrator or dynamically by bootcontroller 202. The virtual WWN assigned to boot gateway 402 is alsoconfigured in switched fabric 108. This authorizes boot gateway 402 tologin to switched fabric 108. Boot gateway 402 communicates with servers102 over control network 110 and eliminates the need for changes made tothe Basic Input Output System (BIOS) code, accomplishing staged bootingof servers 102.

In various embodiments of the invention, multiple boot gateways 402 maybe present in data center 200.

FIG. 5 is a flowchart illustrating a method for dynamically bindingserver 102 to remote disk 106, in accordance with an embodiment of theinvention. At step 502, one or more virtual WWNs are assigned to remotedisk 106. In various embodiments of the invention, the assignment ofvirtual WWNs to remote disk 106 may be performed by one of the datacenter administrator or boot controller 202.

At step 504, boot controller 202 dynamically maps one of the one or morevirtual WWNs to server 102.

In data center 200, when server 102 is powered on, its firmwarebroadcasts a request for booting through an Ethernet NIC on controlnetwork 110. Server 102 subsequently goes into an idle state. Bootcontroller 202 accepts the request of server 102 and provides thecomplete path of bootstrap program 308 to the firmware of server 102.Subsequently, the firmware of server 102 downloads and runs bootstrapprogram 308.

Server 102 and boot controller 202 communicate over control network 110by using standard protocol suites. For example, Pre-executionEnvironment (PXE) is a standard environment to bootstrap computers byusing NICs, which are a combination of Dynamic Host configurationProtocol (DHCP) and Trivial File Transfer Protocol (TFTP). Server 102may broadcast a request for booting by using the DHCP protocol anddownload bootstrap program 308, using the TFTP protocol.

Bootstrap program 308 facilitates communication between boot controller202 and server 102 over control network 110. Boot controller 202 selectsthe server image from which server 102 is required to boot. Thisdecision may be made based on the functional requirements of data center200. Further, the hardware capabilities of server 102 may be examined,corresponding to the server image to be booted. Subsequently, bootcontroller 202 identifies remote disk 106, on which the desired serverimage is located, and communicates this information to server 102. Atstep 506, server 102 boots from remote disk 106 over switched fabric108.

FIG. 6 is a flowchart illustrating a method for dynamically bindingserver 102 to remote disk 106, in accordance with another embodiment ofthe invention. At step 602, one or more virtual WWNs are assigned toremote disk 106. In various embodiments of the invention, the assignmentof virtual WWNs to remote disk 106 may be performed by one of the datacenter administrator or boot controller 202. Boot controller 202 updatesremote disk-to virtual WWN mapping 302, stored in boot configurationdatabase 204. Subsequently, boot controller 202 selects a server imageand identifies remote disk 106, on which the desired server image islocated. Boot controller 202 also examines the hardware capabilities ofserver 102.

At step 604, boot controller 202 dynamically maps one of the one or morevirtual WWNs assigned to remote disk 106 to server 102. Boot controller202 dynamically updates server-to-remote disk mapping 304.

At step 606, boot controller 202 loads bootstrap program 308 on server102. Bootstrap program 308 facilitates communication between bootcontroller 202 and server 102 over control network 110. Boot controller202 communicates server-to-remote disk mapping 304 to server 102.

At step 608, bootstrap program 308 non-persistently passes a first setof initialization parameters to the firmware of HBA 112, installed onserver 102. This initializes the HBA BIOS. Virtual WWN mapped to server102 at step 604 is passed to the firmware of HBA 112. This informationis stored non-persistently on server 102. Thereafter, HBA 112 logs in toswitched fabric 108 and initiates a request to storage device 104 toaccess remote disk 106, according to the SCSI command set. Storagedevice 104 performs authenticity checks on server 102, based on thevirtual WWN mapped to server 102 and the remote disk-to-virtual WWNmapping 302. Subsequently, storage device 104 responds to the requestmade by server 102, in accordance with the SCSI command set.

Further, at step 610, an HBA driver is loaded in the operating systembeing booted on server 102. At step 612, bootstrap program 308non-persistently passes a second set of initialization parameters to theHBA driver. The Virtual WWN mapped to server 102 at step 604 is passedto the HBA driver. The virtual WWN information is stored in the HBAdriver-specific registry keys. This information is storednon-persistently on server 102. The HBA driver, once loaded andinitialized, carries out the complete booting of server 102 over remotedisk 106.

FIG. 7 is a flowchart illustrating a method for dynamically bindingserver 102 to remote disk 106, in accordance with yet another embodimentof the invention. At step 702, at least one virtual WWN is assigned toremote disk 106. In various embodiments of the invention, the assignmentof virtual WWNs to remote disk 106 may be performed by one of the datacenter administrator or boot controller 202.

At step 704, boot controller 202 dynamically maps the assigned virtualWWN to server 102. This authorizes server 102 to access remote disk 106over switched fabric 108.

At step 706, boot gateway 402 executes the first stage of booting server102 over control network 110.

At step 708, the second stage of booting server 102 occurs over switchedfabric 108.

FIGS. 8A and 8B represent a flowchart illustrating a method fordynamically binding server 102 to remote disk 106, in accordance withstill another embodiment of the invention. At step 802, at least onevirtual WWN is assigned to remote disk 106. In various embodiments ofthe invention, the assignment of virtual WWNs to remote disk 106 may beperformed by one of the data center administrator or boot controller202.

At step 804, boot controller 202 dynamically maps the assigned at leastone virtual WWN to server 102. At step 806, a virtual WWN is alsoassigned to remote disk 106. The virtual WWN assigned to remote disk 106at step 806 identifies boot gateway 402, independent of its physicalidentity. Further, the mapping of the virtual WWN to HBA-GW 404 of bootgateway 402 may either be performed statically by the data centeradministrator or dynamically by the boot controller. This authorizesboot gateway 402 to access remote disk 106 over switched fabric 108.

At step 808, boot controller 202 loads bootstrap program 308 on server102 to facilitate the first stage of booting server 102. Bootstrapprogram 308 facilitates the process of server 102 communicating withboot controller 202 and boot gateway 402 over control network 110.

Bootstrap program 308 loads a protocol stack on server 102 by using aset of standard protocols. Subsequently, the driver of the protocolstack loaded on server 102, initiates the first stage of booting server102 by making a request for read/write operations. The drivercommunicates with boot gateway 402 over control network 110, inaccordance with the protocol command set. Boot gateway 402 logs in toswitched fabric 108 by using the virtual WWN mapped onto HBA-GW 404, andaccesses remote disk 106. Boot gateway 402 responds to the driver, inaccordance with the protocol command set, and completes the first stageof booting server 102 over control network 110.

Bootstrap program 308 may load an iSCSI protocol stack on server 102 byusing the PXE protocol, and the iSCSI driver may carry out the firststage of booting server 102 over control network 110.

Subsequently, at step 810, boot gateway 402 loads an HBA driver in theoperating system being booted on server 102. At step 812, bootstrapprogram 308 non-persistently passes a second set of initializationparameters to the HBA driver. At least the one virtual WWN mapped toserver 102 is passed to the HBA driver at step 804. Informationpertaining to at least the one virtual WWN mapped to server 102 isinserted in the HBA driver-specific registry keys. This information isstored non-persistently on server 102. The HBA driver, once loaded andinitialized, carries out the second stage of booting server 102 overremote disk 106.

The invention eliminates the need for persistent mappings andconfigurations to boot the server from the remote disk. The inventionfacilitates communication with servers in a data center when nooperating system is running on the servers. Moreover, the inventionhelps in decoupling the software environment and the configurations fromthe hardware of the server. Further, the invention facilitates theimplementation of server repurposing in a data center. Therefore, theinvention provides the process of booting servers without any change inthe server firmware.

The system for managing requests for a resource in a computer network,as described in the invention or any of its components, may be embodiedin the form of a computer system. Typical examples of a computer systeminclude a general-purpose computer, a programmed microprocessor, amicro-controller, a peripheral integrated circuit element, and otherdevices or arrangements of devices that are capable of implementing thesteps that constitute the method of the invention.

The computer system comprises a computer, an input device, a displayunit, and the Internet. The computer also comprises a microprocessor,which is connected to a communication bus. Moreover, the computerincludes a memory, which may include Random Access Memory (RAM) and ReadOnly Memory (ROM). Further, the computer system comprises a storagedevice, which can be a hard disk drive or a removable storage drive suchas a floppy disk drive, an optical disk drive, etc. The storage devicecan also be other similar means for loading computer programs or otherinstructions into the computer system. Moreover, the computer systemincludes a communication unit, which enables the computer to connect toother databases and the Internet through an I/O interface, andfacilitates the transfer and reception of data from other databases. Thecommunication unit may include a modem, an Ethernet card, or any similardevice, which enables the computer system to connect to databases andnetworks such as LAN, MAN, WAN and the Internet. The computer systemfacilitates inputs from a user through an input device that isaccessible to the system through an I/O interface.

The computer system executes a set of instructions that are stored inone or more storage elements, to process input data. The storageelements may also contain data or other information, as desired. Thesestorage elements may be in the form of an information source or aphysical memory element present in the processing machine.

The set of instructions may include various commands that instruct theprocessing machine to perform specific tasks such as the steps thatconstitute the method of the invention. The set of instructions may bein the form of a software program. The software may be in the form of acollection of separate programs, a program module with a larger program,or a portion of a program module, as in the invention. The software mayalso include modular programming in the form of object-orientedprogramming. Processing of input data by the processing machine may bein response to user commands, results of previous processing, or arequest made by another processing machine. The instructions may beprovided on any suitable computer readable media.

While various embodiments of the invention have been illustrated anddescribed, it will be clear that the invention is not limited to theseembodiments only. Numerous modifications, changes, variations,substitutions and equivalents will be apparent to those skilled in theart, without departing from the spirit and scope of the invention, asdescribed in the claims.

1. A method for remote booting of at least one server from at least oneof a plurality of remote disks in a data center, the at least one serverbeing connected to a Fibre Channel Switched Fabric (FC-SW) through atleast one host bus adapter (HBA), the HBA being assigned a fixed,physical World Wide Name (WWN), the at least one of the plurality ofremote disks being managed by at least one storage device, the at leastone storage device and the at least one server in the data center arephysical devices communicating over the Fibre Channel Switched Fabric,the at least one server, the at least one storage device and the FibreChannel Switched Fabric constituting a Storage Area Network (SAN), thedata center comprising at least one boot controller, the at least oneboot controller being connected to the at least one server through acontrol network, the method comprising the steps of: a. dynamicallyselecting a server image, based on the requirements of the data center,the server image being selected for remote booting of the at least oneserver, the server image being located on the at least one of theplurality of remote disks, the server image being associated with aVirtual World Wide Name (WWN), the Virtual WWN being independent of thephysical WWN of any server in the SAN, wherein the Virtual WWN beingused by the server to establish communications on the FC-SW constitutesthe SAN for the duration of time the selected server image is operatedon the server; b. dynamically assigning the at least one virtual WorldWide Name (WWN) to the at least one of the plurality of remote disksconnected to the Fibre Channel Switched Fabric on the SAN, the at leastone virtual WWN assigned to the at least one of the plurality of remotedisks being independent and mutually exclusive of a physical identity ofthe at least one of the plurality of remote disks; c. dynamicallymapping the assigned virtual WWN to the at least one server, the atleast one server connected to the Fibre Channel Switched Fabric on theSAN, the dynamic mapping authorizing the at least one server to accessthe at least one of the plurality of remote disks to boot the at leastone server, the at least one virtual WWN mapped onto the at least oneserver being independent and mutually exclusive of a physical WWN of theat least one server; and d. remotely booting the at least one serverfrom the selected server image by using the at least one virtual WWN,the at least one virtual WWN representing a virtual identity to uniquelyidentify the physical devices present on the SAN, wherein the at leastone boot controller facilitates dynamic, non-persistent binding betweenthe at least one server and the at least one of plurality of the remotedisks by using the at least one virtual WWN, for remote booting of theat least one server.
 2. The method according to claim 1, wherein bootingthe at least one server comprises loading a bootstrap program on the atleast one server, wherein the bootstrap program facilitatescommunication between the at least one server and the at least one bootcontroller over the control network.
 3. The method according to claim 2,wherein the at least one HBA includes firmware and the method furtherincludes the step of providing a first set of initialization parametersto the firmware of the at least one HBA, the first set of initializationparameters providing the at least one server access to the at least oneof the plurality of remote disks over the Fibre Channel Switched Fabric.4. The method according to claim 3, wherein the first set ofinitialization parameters is provided non-persistently.
 5. The methodaccording to claim 3 further comprising the step of loading an HBAdriver in an operating system booting on the at least one server.
 6. Themethod according to claim 5 further comprising providing a second set ofinitialization parameters to the HBA driver in the operating systembooting on the at least one server, the second set of initializationparameters facilitating further communication between the at least oneserver and the at least one of the plurality of remote disks over theFibre Channel Switched Fabric.
 7. The method according to claim 6,wherein the second set of initialization parameters is providednon-persistently.
 8. The method according to claim 1 further comprisingthe step of maintaining a server-to-remote disk mapping, theserver-to-remote disk mapping facilitating one-to-one associationbetween the at least one server and the at least one of the plurality ofremote disks.
 9. The method according to claim 1 further comprising thestep of maintaining a remote disk-to-virtual WWN mapping, the remotedisk-to-virtual WWN mapping facilitating authorizing the at least oneserver to access the at least one of the plurality of remote disks. 10.The method according to claim 1 further comprising the step ofconfiguring the remote disk-to-virtual WWN mapping in the Fibre ChannelSwitched Fabric, wherein the remote disk-to-virtual mapping facilitatesdynamic assignment of the at least one Virtual WWN to the at least oneof the plurality of remote disks.
 11. The method according to claim 1,wherein the control network further provides communication between theat least one boot controller and the at least one storage device, the atleast one storage device managing the at least one of the plurality ofremote disks.
 12. The method according to claim 1, wherein the serverimage comprises an operating system, a set of drivers specific to theoperating system, the operating system configuration data, and theapplication software.
 13. A method for remote booting of at least oneserver from at least one of a plurality of remote disks in a datacenter, the at least one server being connected to a Fibre ChannelSwitched Fabric (FC-SW) through at least one host bus adapter (HBA), theHBA being assigned a fixed, physical World Wide Name (WWN), the at leastone of the plurality of remote disks being managed by at least onestorage device, the at least one storage device and the at least oneserver in the data center are physical devices communicating over theFibre Channel Switched Fabric, the at least one server, the at least onestorage device and the Fibre Channel Switched Fabric constituting aStorage Area Network (SAN), the data center comprising at least one bootcontroller, the at least one boot controller being connected to the atleast one server through a control network, the data center furthercomprising at least one boot gateway, the at least one boot gatewaybeing connected to the Fibre Channel Switched Fabric through at leastone boot gateway host bus adapter (HBA-GW), the at least one bootgateway further being connected to the control network and constitutinga part of the SAN, the method comprising the steps of: a. dynamicallyselecting a server image, based on the requirements of the data center,the server image being selected for remote booting of the at least oneserver, the server image being located on the at least one of theplurality of remote disks, the server image being associated with aVirtual World Wide Name (WWN), the Virtual WWN being independent of thephysical WWN of any server in the SAN, wherein the Virtual WWN beingused by the server to establish communications on the FC-SW constitutesthe SAN for the duration of time the selected server image is operatedon the server; b. dynamically assigning the at least one virtual WorldWide Name (WWN) to the at least one of the plurality of remote disksconnected to the Fibre Channel Switched Fabric on the SAN, the at leastone virtual WWN assigned to the at least one of the plurality of remotedisks being independent and mutually exclusive of a physical identity ofthe at least one of the plurality of remote disks; c. dynamicallymapping the assigned virtual WWN to the at least one server, the dynamicmapping authorizing the at least one server to access the at least oneof the plurality of remote disks to boot the at least one server, the atleast one server connected to the Fibre Channel Switched Fabric on theSAN, the at least one virtual WWN mapped onto the at least one server,being independent and mutually exclusive of a physical WWN of the atleast one server; d. remotely booting the at least one server from theselected server image, the at least one server being booted until afirst stage over the control network through the at least one bootgateway, the at least one boot gateway accessing the at least one of theplurality of remote disks over the Fibre Channel Switched Fabric; and e.booting the at least one server until a second stage, the at least oneserver being booted until the second stage over the Fibre ChannelSwitched Fabric by using the at least one virtual WWN, the at least onevirtual WWN representing a virtual identity to uniquely identify thephysical devices present on the SAN, the at least one server accessingthe at least one of the plurality of remote disks over the Fibre ChannelSwitched Fabric, wherein the at least one boot controller facilitatesdynamic, non-persistent binding between the at least one server and theat least one of plurality of the remote disks by using the at least onevirtual WWN, for remote booting of the at least one server.
 14. Themethod according to claim 13, wherein the step of booting the at leastone server until the first stage further comprises loading a bootstrapprogram on the at least one server.
 15. The method according to claim14, wherein the bootstrap program facilitates communication between theat least one server and the at least one boot controller over thecontrol network.
 16. The method according to claim 14, wherein thebootstrap program further facilitates communication between the at leastone server and the one of the at least one boot gateway over the controlnetwork.
 17. The method according to claim 14, wherein the step ofbooting the at least one server until the first stage further comprisesloading an HBA driver in an operating system booting on the at least oneserver, the step of booting the at least one server further comprisingproviding a first set of initialization parameters required forestablishing a communication between the at least one server and the atleast one boot gateway, the first set of initialization parametersproviding the at least one server access to the at least one of theplurality of remote disks, the first set of initialization parametersbeing provided non-persistently.
 18. The method according to claim 14further comprising the step of providing a second set of initializationparameters to the HBA driver in the operating system booting on the atleast one server, the second set of initialization parametersfacilitating the second stage of booting of the at least one server,whereby the at least one server communicates with the at least one ofthe plurality of remote disks over the Fibre Channel Switched Fabric.19. The method according to claim 18, wherein the second set ofinitialization parameters is non-persistent.
 20. The method according toclaim 13 further comprising the step of maintaining a server-to-remotedisk mapping, wherein the server-to-remote disk mapping facilitatesone-to-one association between the at least one server and the at leastone of the plurality of remote disks.
 21. The method according to claim13 further comprising the step of maintaining a remote disk-to-virtualWWN mapping, wherein the remote disk-to-virtual WWN mapping facilitatesauthorizing the at least one server and the one of the at least one bootgateway to access the at least one of the plurality of remote disks. 22.The method according to claim 13 further comprising the step ofconfiguring the remote disk-to-virtual WWN mapping in the Fibre ChannelSwitched Fabric, whereby the at least one server and the one of the atleast one boot gateway are authorized to log in to the Fibre ChannelSwitched Fabric.
 23. The method according to claim 13, wherein theserver image comprises an operating system, a set of drivers specific tothe operating system, the operating system configuration data, and theapplication software.
 24. A system for remote booting of at least oneserver from at least one of a plurality of remote disks, the at leastone server being connected to a Fibre Channel Switched Fabric (FC-SW)through at least one host bus adapter (HBA), the HBA being assigned afixed, physical World Wide Name (WWN), the at least one of the pluralityof remote disks being managed by at least one storage device, the atleast one storage device and the at least one server in the data centerare physical devices communicating over the Fibre Channel SwitchedFabric, the at least one server, the at least one storage device and theFibre Channel Switched Fabric constituting a Storage Area Network (SAN),the system comprising: a. a boot configuration database, the bootconfiguration database storing a remote disk-to-virtual World Wide Name(WWN) mapping, the remote disk-to-virtual WWN mapping comprisinginformation related to the assignment of at least one virtual WWN to theat least one of the plurality of remote disks, the at least one virtualWWN being assigned dynamically to the at least one of the plurality ofremote disks connected to the Fibre Channel Switched Fabric on the SAN,the at least one virtual WWN assigned to the at least one of theplurality of remote disks being independent and mutually exclusive of aphysical identity of the at least one of the plurality of remote disks;b. at least one boot controller, the at least one boot controllerperforming: dynamically selecting a server image, based on therequirements of the data center, the server image being selected forremote booting of the at least one server, the server image beinglocated on the at least one of the plurality of remote disks, the serverimage being associated with a Virtual World Wide Name (WWN), the VirtualWWN being independent of the physical WWN of any server in the SAN,wherein the Virtual WWN being used by the server to establishcommunications on the FC-SW constitutes the SAN for the duration of timethe selected server image is operated on the server; dynamically mappingthe assigned virtual WWN to the at least one server, the dynamic mappingauthorizing the at least one server to access the at least one of theplurality of remote disks to boot the at least one server, the at leastone server connected to the Fibre Channel Switched Fabric on the SAN,the at least one virtual WWN mapped onto the at least one server beingindependent and mutually exclusive of a physical WWN of the at least oneserver; and remotely booting the at least one server from the selectedserver image by using the at least one virtual WWN, the at least onevirtual WWN representing a virtual identity to uniquely identify thephysical devices present on the SAN, the at least one boot controllerfacilitating dynamic, non-persistent binding between the at least oneserver and the at least one of plurality of the remote disks by usingthe at least one virtual WWN, for remote booting of the at least oneserver; and c. a control network, the control network providingcommunication between the at least one boot controller, the at least onestorage device and the at least one server.
 25. The system according toclaim 24, wherein the remote disk-to-virtual WWN mapping permitsauthorizing the at least one server to access the at least one of theplurality of remote disks, wherein the remote disk-to-virtual mappingfacilitates dynamic assignment of the at least one Virtual WWN to the atleast one of the plurality of remote disks.
 26. The system according toclaim 24, wherein the boot configuration database further comprises aserver-to-remote disk mapping, the server-to-remote disk mappingcomprising information related to the association between the at leastone server and the at least one of the plurality of remote disks, theserver-to-remote disk mapping being updated dynamically, theserver-to-remote disk mapping facilitating one-to-one associationbetween the at least one server and the at least one of the plurality ofremote disks.
 27. The system according to claim 24, wherein the bootconfiguration database further comprises a repository of at least onevirtual WWN.
 28. The system according to claim 24, wherein the bootconfiguration database further comprises a bootstrap program, thebootstrap program facilitating communication between the at least oneserver and the at least one boot controller over the control network.29. The system according to claim 24, wherein the at least one bootcontroller loads the bootstrap program on the at least one server overthe control network, the bootstrap program facilitating communicationbetween the at least one server and the at least one boot controllerover the control network.
 30. The system according to claim 29, whereinthe bootstrap program provides a first set of initialization parametersto a the firmware of the at least one HBA, the first set ofinitialization parameters providing the at least one server access tothe at least one of the plurality of remote disks, the first set ofinitialization parameters being provided non-persistently.
 31. Thesystem according to claim 30, wherein the bootstrap program loads an HBAdriver in an operating system booting on the at least one server. 32.The system according to claim 31, wherein the bootstrap program furtherprovides a second set of initialization parameters to the HBA driver inan operating system booting on the at least one server, the second setof initialization parameters facilitating further communication betweenthe at least one server and the at least one of the plurality of remotedisks over the Fibre Channel Switched Fabric, the second set ofinitialization parameters being provided non-persistently.
 33. Thesystem according to claim 24, wherein the at least one boot controllerdynamically updates a server-to-remote disk mapping stored in the bootconfiguration database, the server-to-remote disk mapping comprisinginformation related to the association between the at least one serverand the at least one of the plurality of remote disks.
 34. The systemaccording to claim 24, wherein the at least one boot controller updatesthe remote disk-to-virtual WWN mapping stored in the boot configurationdatabase, the remote disk-to-virtual WWN mapping comprising informationrelated to the assignment of at least one virtual WWN to the at leastone of the plurality of remote disks.
 35. The system according to claim24, wherein the control network further provides communication betweenthe at least one boot controller and the at least one storage device,the at least one storage device managing the at least one of theplurality of remote disks.
 36. The system according to claim 24, whereinthe Fibre Channel Switched Fabric is configured with the remotedisk-to-virtual WWN mapping, wherein the remote disk-to-virtual mappingfacilitates dynamic assignment of the at least one Virtual WWN to the atleast one of the plurality of remote disks.
 37. A system for remotebooting at least one server from at least one of a plurality of remotedisks, the at least one server being connected to a Fibre ChannelSwitched Fabric (FC-SW) through at least one host bus adapter (HBA), theHBA being assigned a fixed, physical World Wide Name (WWN), the at leastone of the plurality of remote disks being managed by at least onestorage device, the at least one storage device and the at least oneserver in the data center are physical devices communicating over theFibre Channel Switched Fabric, the at least one server, the at least onestorage device and the Fibre Channel Switched Fabric constituting aStorage Area Network (SAN), the system comprising: a. a bootconfiguration database, the boot configuration database storing a remotedisk-to-virtual World Wide Name (WWN) mapping, the remotedisk-to-virtual WWN mapping comprising information related to theassignment of at least one virtual WWN to the at least one of theplurality of remote disks, the remote disk-to-virtual WWN mapping beingupdated, the at least one virtual WWN being assigned dynamically to theat least one of the plurality of remote disks connected to the FibreChannel Switched Fabric on the SAN, the at least one virtual WWNassigned to the at least one of the plurality of remote disks beingindependent and mutually exclusive of a physical identity of the atleast one of the plurality of remote disks; b. at least one bootcontroller, the at least one boot controller performing: dynamicallyselecting a server image, based on the requirements of the data center,the server image being selected for remote booting of the at least oneserver, the server image being located on the at least one of theplurality of remote disks, the server image being associated with aVirtual World Wide Name (WWN), the Virtual WWN being independent of thephysical WWN of any server in the SAN, wherein the Virtual WWN beingused by the server to establish communications on the FC-SW constitutesthe SAN for the duration of time the selected server image is operatedon the server; dynamically mapping the assigned WWN to the at least oneserver, the dynamic mapping authorizing the at least one server toaccess the at least one of the plurality of remote disks to boot the atleast one server, the at least one server connected to the Fibre ChannelSwitched Fabric on the SAN, the at least one virtual WWN mapped onto theat least one server being independent and mutually exclusive of aphysical WWN of the at least one server; and remotely booting the atleast one server from the selected server image by using the at leastone virtual WWN, the at least one virtual WWN representing a virtualidentity to uniquely identify the physical devices present on the SAN,the at least one boot controller facilitates dynamic, non-persistentbinding between the at least one server and the at least one ofplurality of the remote disks by using the at least one virtual WWN, forremote booting of the at least one server; c. at least one boot gateway,the at least one boot gateway facilitating a first stage of booting ofthe at least one server; and d. a control network, the control networkproviding communication between the at least one server, the at leastone boot gateway, the at least one storage device, and the at least oneboot controller.
 38. The system according to claim 37, wherein theremote disk-to-virtual WWN mapping further comprises information relatedto the assignment of a virtual WWN to the at least one of the pluralityof remote disks, the virtual WWN uniquely identifying one of the atleast one boot gateway independent of a physical identity of the one ofthe at least one boot gateway.
 39. The system according to claim 37,wherein the remote disk-to-virtual WWN mapping facilitates authorizingthe at least one server and the one of the at least one boot gateway toaccess the at least one of the plurality of remote disks.
 40. The systemaccording to claim 37, wherein the boot configuration database furthercomprises a server-to-remote disk mapping, the server-to-remote diskmapping comprising information related to the association between the atleast one server and the at least one of the plurality of remote disks,the server-to-remote disk mapping being updated dynamically.
 41. Thesystem according to claim 40, wherein the server-to-remote disk mappingfacilitates one-to-one association between the at least one server andthe at least one of the plurality of remote disks.
 42. The systemaccording to claim 37, wherein the boot configuration database furthercomprises a repository of a plurality of virtual WWNs.
 43. The systemaccording to claim 37, wherein the boot configuration database furthercomprises a bootstrap program, the bootstrap program facilitatingcommunication between the at least one server and the at least one bootcontroller over the control network.
 44. The system according to claim37, wherein the at least one boot controller assigns the one of the atleast one boot gateway to the at least one server.
 45. The systemaccording to claim 37, wherein the at least one boot controllerinitiates the first stage of booting of the at least one server, theboot controller loading a bootstrap program on the at least one serverover the control network, the bootstrap program facilitatingcommunication between the at least one server and the at least one bootcontroller over the control network.
 46. The system according to claim45, wherein the bootstrap program further facilitates communicationbetween the at least one server and the one of at least one boot gatewayover the control network.
 47. The system according to claim 45, whereinthe bootstrap program loads an HBA driver in the operating systembooting on the at least one server over the control network through theone of the at least one boot gateway, the one of the at least one bootgateway accessing the remote disk over the Fibre Channel SwitchedFabric.
 48. The system according to claim 47, wherein the bootstrapprogram further provides a second set of initialization parameters tothe HBA driver in the operating system booting on the at least oneserver, the second set of initialization parameters facilitating asecond stage of booting of the at least one server, whereby the at leastone server accesses the at least one of the plurality of remote disksover the Fibre Channel Switched Fabric, the second set of initializationparameters being provided non-persistently.
 49. The system according toclaim 37, wherein the at least one boot controller dynamically updates aserver-to-remote disk mapping stored in the boot configuration database,the server-to-remote disk mapping comprising information related to theassociation between the at least one server and the at least one of theplurality of remote disk.
 50. The system according to claim 37, whereinthe at least one boot controller updates the remote disk-to-virtual WWNmapping stored in the boot configuration database, the remotedisk-to-virtual WWN mapping comprising information related to theassignment of at least one virtual WWN to the at least one of theplurality of remote disks.
 51. The system according to claim 37, whereinthe control network further provides communication between the at leastone boot controller and the at least one storage device, the at leastone storage device managing the at least one of the plurality of remotedisks.
 52. The system according to claim 37, wherein the Fibre ChannelSwitched Fabric is configured with the remote disk-to-virtual WWNmapping, whereby the at least one server and the one of the at least oneboot gateway are authorized to log in to the Fibre Channel SwitchedFabric.
 53. A computer program product, disposed on a computernon-transitory computer readable storage medium, for remote booting atleast one server from at least one of a plurality of remote disks in adata center, the at least one server being connected to a Fibre ChannelSwitched Fabric (FC-SW) through at least one host bus adapter (HBA), theHBA being assigned a fixed, physical World Wide Name (WWN), the at leastone of the plurality of remote disks being managed by at least onestorage device, the at least one storage device and the at least oneserver in the data center are physical devices communicating over theFibre Channel Switched Fabric, the at least one server, the at least onestorage device and the Fibre Channel Switched Fabric constituting aStorage Area Network (SAN), the data center comprising at least one bootcontroller, the at least one boot controller being connected to the atleast one server through a control network, the computer program productcomprising: a. a program instruction means for dynamically selecting aserver image, based on the requirements of the data center, the serverimage being selected for remote booting of the at least one server, theserver image being located on the at least one of the plurality ofremote disks, the server image being associated with a Virtual WorldWide Name (WWN), the Virtual WWN being independent of the physical WWNof any server in the SAN, wherein the Virtual WWN being used by theserver to establish communications on the FC-SW constitutes the SAN forthe duration of time the selected server image is operated on theserver; b. a program instruction means for dynamically assigning the atleast one virtual World Wide Name (WWN) to the at least one of theplurality of remote disks connected to the Fibre Channel Switched Fabricon the SAN, the at least one virtual WWN assigned to the at least one ofthe plurality of remote disks being independent and mutually exclusiveof a physical identity of the at least one of the plurality of remotedisks; c. a program instruction means for dynamically mapping theassigned virtual WWN to the at least one server, the dynamic mappingauthorizing the at least one server to access the at least one of theplurality of remote disks to boot the at least one server, the at leastone server connected to the Fibre Channel Switched Fabric on the SAN,the at least one virtual WWN mapped onto the at least one server beingindependent and mutually exclusive of a physical identity WWN of the atleast one server; and d. a program instruction means for remotelybooting the at least one server from the selected server image by usingthe at least one virtual WWN, the at least one virtual WWN representinga virtual identity to uniquely identify the physical devices present onthe SAN, wherein the at least one boot controller facilitates dynamic,non-persistent binding between the at least one server and the at leastone of plurality of the remote disks by using the at least one virtualWWN, for remote booting of the at least one server.
 54. The computerprogram product according to claim 53 further comprising programinstruction means for providing a first set of initialization parametersto the firmware of the at least one HBA, the first set of initializationparameters providing the at least one server access to the at least oneof the plurality of remote disks.
 55. The computer program productaccording to claim 54 further comprising program instruction means forproviding a second set of initialization parameters to an HBA driver inthe operating system booting on the at least one server, the second setof initialization parameters facilitating further communication betweenthe at least one server and the at least one of the plurality of remotedisks over the Fibre Channel Switched Fabric.
 56. A computer programproduct, disposed on a computer non-transitory computer readable storagemedium, for remote booting at least one server from at least one of aplurality of remote disks in a data center, the at least one serverbeing connected to a Fibre Channel Switched Fabric (FC-SW) through atleast one host bus adapter (HBA), the HBA being assigned a fixed,physical World Wide Name (WWN), the at least one of the plurality ofremote disks being managed by at least one storage device, the at leastone storage device and the at least one server in the data center arephysical devices communicating over the Fibre Channel Switched Fabric,the at least one server, the at least one storage device and the FibreChannel Switched Fabric constituting a Storage Area Network (SAN), thedata center comprising at least one boot controller, the at least oneboot controller being connected to the at least one server through acontrol network, the data center further comprising at least one bootgateway, the at least one boot gateway being connected to the FibreChannel Switched Fabric through at least one boot gateway host busadapter (H BA-GW), the at least one boot gateway further being connectedto the control network, the computer program product comprising: a. aprogram instruction means for dynamically selecting a server image,based on the requirements of the data center, the server image beingselected for remote booting of the at least one server, the server imagebeing located on the at least one of the plurality of remote disks, theserver image being associated with a Virtual World Wide Name (WWN), theVirtual WWN being independent of the physical WWN of any server in theSAN, wherein the Virtual WWN being used by the server to establishcommunications on the FC-SW constituting the SAN for the duration oftime the selected server image is operated on the server; b. a programinstruction means for dynamically assigning the at least one virtualWorld Wide Names (WWN) to the at least one of the plurality of remotedisks connected to the Fibre Channel Switched Fabric on the SAN, the atleast one virtual WWN assigned to the at least one of the plurality ofremote disks being independent and mutually exclusive of a physicalidentity of the at least one of the plurality of remote disks; c. aprogram instruction means for dynamically mapping the assigned virtualWWN to the at least one server, the at least one server connected to theFibre Channel Switched Fabric on the SAN, the dynamic mappingauthorizing the at least one server to access the at least one of theplurality of remote disks to boot the at least one server, the at leastone virtual WWN mapped onto the at least one server being independentand mutually exclusive of a physical identity WWN of the at least oneserver; d. a program instruction means for remotely booting the at leastone server using the selected server image by using the at least onevirtual WWN, the at least one virtual WWN representing a virtualidentity to uniquely identify the physical devices present on the SAN,the at least one server being booted until a first stage over thecontrol network through the at least one boot gateway, the at least oneboot gateway accessing the at least one of the plurality of remote disksover the Fibre Channel Switched Fabric; and e. a program instructionmeans for booting the at least one server until a second stage, the atleast one server being booted until the second stage over the FibreChannel Switched Fabric, the at least one server accessing the at leastone of the plurality of remote disks over the Fibre Channel SwitchedFabric wherein the at least one boot controller facilitates dynamic,non-persistent binding between the at least one server and the at leastone of plurality of the remote disks by using the at least one virtualWWN, for remote booting of the at least one server.
 57. The computerprogram product according to claim 56 further comprising programinstruction means for providing a first set of initialization parametersto the firmware of the at least one HBA, the first set of initializationparameters providing the at least one server access to the at least oneof the plurality of remote disks.
 58. The computer program productaccording to claim 57 further comprising program instruction means forproviding a second set of initialization parameters to an HBA driver inthe operating system booting on the at least one server, the second setof initialization parameters facilitating further communication betweenthe at least one server and the at least one of the plurality of remotedisks over the Fibre Channel Switched Fabric.